Conversation
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughBarrel export now publicly re-exports Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Review rate limit: 0/1 reviews remaining, refill in 50 minutes and 57 seconds.Comment |
Codecov Report❌ Patch coverage is
❌ Your patch status has failed because the patch coverage (0.00%) is below the target coverage (80.00%). You can increase the patch coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## main #110 +/- ##
==========================================
- Coverage 30.24% 30.23% -0.01%
==========================================
Files 161 161
Lines 6230 6232 +2
==========================================
Hits 1884 1884
- Misses 4346 4348 +2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In
`@packages/stream_core_flutter/lib/src/components/accessories/stream_emoji.dart`:
- Around line 331-335: The platform-based fontFamily switch in stream_emoji.dart
can return 'Segoe UI Emoji' for Windows even on web, which desyncs with the
Noto-specific web scaling; update the switch expression used to set fontFamily
(the variable named fontFamily) so that Windows is only selected when not kIsWeb
(i.e., use .windows when !kIsWeb), forcing web builds to fall through to 'Noto
Color Emoji'; apply the same guard change to the other identical switch/site
referenced (the second fontFamily switch around the other usage) so all web code
paths consistently use Noto Color Emoji.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 51557936-e91f-41ff-a2f8-e20500f284d4
📒 Files selected for processing (1)
packages/stream_core_flutter/lib/src/components/accessories/stream_emoji.dart
Submit a pull request
CLA
Description of the pull request
This exports the default emoji, so it's easier to customize it.
Summary by CodeRabbit